Using A Kettle Job In Campaign Manager

After a Kettle job has been created and successfully tested in the ETL tool, it can be configured for use in Campaign Manager.

In this example, the Settings tool is configured to use a Kettle job. It has been associated with the Twitter Tactic with permissions granted to the Campaign Manager user.

Refer to the Campaign Manager Administration Guide for instructions on how to configure a Kettle job for use in Campaign Manager. The guide will show how permissions can be applied to allow only certain users to see and use this Job.

At this point the Kettle script is available to the user and could be used in a number of scenarios based on its contents.

The Fields tab on the tactic shows the columns from the Kettle transformation and these should be mapped to their respective Engine columns.

Configuration is now complete. When the campaign runs, the transformation will change the delimiter and the following values will be added to the campaign history:

• [Campaign History].[Demo_History].[ChannelType] = Twitter
• [Campaign History].[Demo_History].[ChannelName] = Twitter account 1
• [Campaign History].[Demo_History].[Creative Name] = CC_Offer_4

• Integrations between Campaign Manager and Kettle
  • External Integrations Pack
  • Terminology Used in Integrations
  • File Tactic Integration
  • Omni Tactic Integration
  • Profile Rule Export Tool Integration
  • Injecting a Custom Transformation Into an Output Tactic
  • Data Input and Integration Points
  • Creating a Kettle script
  • Using a Kettle Job in Campaign Manager
  • Example code